-
Notifications
You must be signed in to change notification settings - Fork 6.3k
8369178: G1: Use NMethodMarkingScope and ThreadsClaimTokenScope in G1RootProcessor #27644
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
👋 Welcome back fandreuzzi! A progress list of the required criteria for merging this PR into |
@fandreuz This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 15 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@albertnetymk) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
StrongRootsScope _srs; | ||
NMethodMarkingScope _nmethod_marking_scope; | ||
ThreadsClaimTokenScope _threads_claim_token_scope; | ||
bool _is_parallel; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would have used uint _num_workers
, but I guess this also works.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't need to know how many workers there are, just if we are parallel or not. I think this goes in the same direction as the idea of the PR, being clear about what we actually need
/cc hotspot-gc |
@albertnetymk |
/integrate |
Replace
StrongRootsScope
withThreadsClaimTokenScope
andMarkingNMethodClosure
inG1RootProcessor
to be more precise with what is needed and why.MarkingNMethodClosure
is used inG1FullGCMarkTask
, so we also needNMethodMarkingScope
.active_workers
is guaranteed to be> 0
Passes tier1 and tier2 (fastdebug).
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/27644/head:pull/27644
$ git checkout pull/27644
Update a local copy of the PR:
$ git checkout pull/27644
$ git pull https://git.openjdk.org/jdk.git pull/27644/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 27644
View PR using the GUI difftool:
$ git pr show -t 27644
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/27644.diff
Using Webrev
Link to Webrev Comment